/*
 *
 *
 *Rough Notes on the whole concept of "Meta" information in graphs and nodes:
 *
 *
 *What use cases could you use MetaData for:
 *
 *
 * Connecting Graphy results back to their data source
 *          i.e., - in a complicated CompoundGraph query where like data is obtained from
 *          multiple sources such as RDF on the web, XML files and SQL servers, being able to
 *          ask a given result node which datasource it came from empowers the user
 *          to be more independent of Graphy in subsequent tasks - i.e., to simple take the resulting node
 *          and perform more low level XML Processing on the original document.
 *    further ideas:
 *    In CompoundGraph queries, node meta data should be able to provide simple expressions on how
 *    to retrieve the native data directly outside of Graphy.
 *    i.e., node.getMetaContext().getDataSource and getIdentityQuery expression
 *
 *
 * Heuristics in CompoundGraph traversals
 *   i.e, if a PathTraverser predicate tree has an "AND NOT()"
 *        predicate chain between two parallel SourceGraphs in a compound Graph,
 *        an optimized graph query engine could choose to evaluate both sides of the tree independently
 *        before trying to merge them by breaking the main query into subqueries using meta information
 * Ascribing properties to objects based on MetaGraph info
 *   - i.e., If personGraph came from a database, automatically add a "confirmed" property to an object
 *           as opposed to "unconfirmed" property if it's from an XML file.
 *
 * Queries into compound Graphs need QueryContext based information to support intelligent, "Context" based queries.
 * i.e., If a user wants to query a family tree with a PathTraverser, being able to express "only go 3 generations deep"
 * needs some kind of PathMetaData to express it.
 *
 */

package net.metashare.grah.meta

/**
 *
 * @author dsherema
 */
class MetaContext {

}

